From - Mon Feb 24 10:55:47 1997 Return-Path: pqueiros@cisco.com Received: from europe.cisco.com (europe.cisco.com [171.68.135.98]) by mail.telepac.pt (8.8.4/0.0) with ESMTP id UAA25567 for ; Fri, 21 Feb 1997 20:15:02 GMT Received: from sales-pqueiros.cisco.com (gor-ppp2.cisco.com [171.68.137.9]) by europe.cisco.com (8.8.5/8.8.5) with SMTP id VAA14931 for ; Fri, 21 Feb 1997 21:13:15 GMT Message-Id: <2.2.32.19970221201009.00bde004@europe.cisco.com> X-Sender: pqueiros@europe.cisco.com X-Mailer: Windows Eudora Pro Version 2.2 (32) Mime-Version: 1.0 Date: Fri, 21 Feb 1997 20:10:09 +0000 To: Computer 2000 Portuguesa From: Pedro Queiros Subject: Re: 7xx config problem w. PAP/CHAP (was TAC Case F34281) Content-Type: text/plain; charset="us-ascii" Status: X-Mozilla-Status: 0011 Content-Length: 23458 Ze Frances. Ja esta OK o 765 na Telepac. Pedro >Return-Path: >X-Sender: laird@rottweiler.cisco.com >Date: Thu, 20 Feb 1997 19:37:46 -0800 >To: Mario Tomaz , jzuo@cisco.com (Jean Zuo), > pqueiros@europe.cisco.com >From: Bruce Laird >Subject: Re: 7xx config problem w. PAP/CHAP (was TAC Case F34281) >Cc: laird@europe.cisco.com, ahowarth@europe.cisco.com, eda@europe.cisco.com, > marsolie@europe.cisco.com, ccarball@europe.cisco.com, > nmoulton@cisco.com > >Mario and Jean, > >This is great! Thanks for sticking with it. > >Pedro, > >Are you comfortable now to sell the 7xx's? > >BGL > >At 6:22 PM +0000 2/20/97, Mario Tomaz wrote: >>Jean, >> >>Yesterday I took the initiative and did the test myself. Now I included the >>command "SET PPP AU OUT NONE". >>This prooved indeed to solve the problem. >> >>After this I contacted the customer, asked him to do the test on his own, >>and he confirmed today that this problem is gone. >> >>So guys, thank you all for your concern and help. I will never forget this >>command again. >> >>Cesar could you close the case? >> >>Regards, >>Mario Tomaz >> >> >> >>Jean, >> >>Last week I was in Paris for training. I am now trying to organize the test. >>I will know more in a few days. >> >>Thanks so far, >>Mario Tomaz >> >>At 20:37 18-02-1997 -0800, you wrote: >>>Mario, >>> >>>Haven't heard from you for almost a week. I am wondering whether you have >>>the chance to try out my suggestion, and whether the set-up is working >>>after the configuration modification. >>> >>>Please provide us the status. Thanks! >>> >>> >>> >>>>X-Sender: jzuo@chow.cisco.com >>>>Mime-Version: 1.0 >>>>X-Priority: 2 (High) >>>>Date: Wed, 12 Feb 1997 15:19:17 -0800 >>>>To: mtomaz@cisco.com, ccarball@cisco.com >>>>From: jzuo@cisco.com (Jean Zuo) >>>>Subject: Re: 7xx config problem w. PAP/CHAP (was TAC Case F34281) >>>>Cc: laird, jzuo, pqueiros, ahowarth, eda, marsolie >>>> >>>>Mario, >>>> >>>>It sounds like the 700 is set up to do out going authentication (i.e. to >>>>authenticate the device that it calls to.) To disable this, use the >>>>following command: >>>> >>>>SET PPP AU OUT NONE >>>> >>>>Invoke this command from within the user-define profile which is used to >>>>connect to the 5200. Let's see if this should take care of the problem. >>>>BTW, for 4.0 release the default is already set to none so you don't have >>>>to do this. >>>> >>>>In the meantime, I will check with Art to see if his staff and dial-up >>>>set-up are available to try the scenario out. >>>> >>>> >>>> >>>>>X-Sender: laird@rottweiler.cisco.com (Unverified) >>>>>Mime-Version: 1.0 >>>>>X-Priority: 2 (High) >>>>>Date: Tue, 11 Feb 1997 14:34:42 -0800 >>>>>To: jzuo@cisco.com, Mario Tomaz , ccarball@cisco.com >>>>>From: Bruce Laird >>>>>Subject: Re: 7xx config problem w. PAP/CHAP (was TAC Case F34281) >>>>>Cc: pqueiros@europe.cisco.com, ahowarth@cisco.com, eda@cisco.com, >>>>> marsolie@cisco.com, laird@cisco.com >>>>> >>>>>Mario, >>>>> >>>>>Thanks, I'm forwarding your email to Jean Zuo (PME for SOHO Products). >>>>>I'm also CC'ing Art Howarth (ABU PME Mgr), Ed Alcoff (7xx PM), >>>>>Cesar Carballes (Brussels TAC), and Corinne Marsolier (EMEA ISDN Product >>>>>Marketing), because they should be kept informed as to resolution. >>>>> >>>>> >>>>>Jean, >>>>> >>>>>Please consult with Art Howarth on this to see if it is just a question >>>>>of the correct configuration commands. If it is more complicated, >>>>>please consult with Ed Alcoff to come up with a get-well plan, and >>>>>advise us all in either event. >>>>> >>>>>Mario and Cesar, >>>>> >>>>>For future reference, Art Howarth has a dial-up lab in San Jose, where >>>>>he and his PMEs have extensively tested and documented 7xx<-->AS5200, >>>>>and 7xx<-->Ascend connectivity scenarios. I'm sure they have a work >>>>>around for this type of PAP/CHAP interoperability. >>>>> >>>>>In the future, please don't wait 2 months to up-level this type of >>>>>problem! You should feel OK to bring these kinds of problems and Qs >>>>>to the attention of either Jean Zuo or Ed Alcoff. >>>>> >>>>>Thanks, >>>>>BGL >>>>> >>>>>At 12:36 PM +0000 2/11/97, Mario Tomaz wrote: >>>>>>Bruce, >>>>>> >>>>>>The authentication process of the 765 USER seems to work properly. After >>>>>>this the 765 waits for the AS5200 to authenticate itself back to the >>>>>>765. We >>>>>>can't disable this last process. >>>>>>If the command "ppp pap sent-username as5200 password yyyy" is not >>>>>>included >>>>>>in the AS5200 configuration then the authentication process is invalid and >>>>>>the 765 disconnects. >>>>>>We have tested the same with a 765 accessing a 25xx router. The same >>happens. >>>>>>I insist that the 765 is causing this problem. There is no reason why it >>>>>>should wait for the Access server to authenticate itself back to the 765. >>>>>> >>>>>>I have a case open at the TAC (F34281) since the beginning of December. >>>>>>Cesar Carballes at the Brussels TAC is able to tell you all the details. >>>>>> >>>>>>Regards, >>>>>>Mario Tomaz >>>>>> >>>>>>>Date: Tue, 04 Feb 1997 17:46:24 +0000 >>>>>>>To: Cesar Carballes >>>>>>>From: Mario Tomaz >>>>>>>Subject: Re: Case F34281 >>>>>>>Cc: pqueiros, hcarlos >>>>>>>X-Attachments: C:\Data\Email\Attachments\765_aut.syc; >>>>>>C:\Data\Email\Attachments\Isdn_pap.syc; >>>>>>C:\Data\Email\Attachments\Papno_ok.syc; >>>>>>> >>>>>>> >>>>>>>Cesar, >>>>>>> >>>>>>>Our partner Convex, did a lot of testing. The authentication process was >>>>>>configured as you advised. The same problem persists. >>>>>>> >>>>>>>I am including some traces captured with the Sniffer to show you what >>>>>>>happens. >>>>>>>The cause of the problem seems to be lying on the authentication >>>>>>>process on >>>>>>the 765. The customer is planning to use PAP authentication despite all >>this. >>>>>>>Isn't there anybody else with the same configuration and the same >>>>>>>problem? >>>>>>> >>>>>>>Please take the necessary steps to speed up the activity concerning this >>>>>>case. We are dealing with a Internet Service provider, 100's of 765's are >>>>>>involved in this project and the customer is threatening to move over >>>>>>to the >>>>>>competition. >>>>>>> >>>>>>>Regards, >>>>>>>Mario Tomaz >>>>>>> >>>>>>>At 17:37 24-01-1997 +0100, you wrote: >>>>>>>>Hello again Tomaz, >>>>>>>> >>>>>>>>The 16 january I asked you to setup the 765 using >>>>>>>>ppp authentication outgoing pap >>>>>>>>>by default is set to incoming. >>>>>>>>Did you tried? Your last email saids that is not working, is this after >>>>>>>>implementing this command? >>>>>>>> >>>>>>>>Kind Regards >>>>>>>>Cesar Carballes >>>>>>>> >>>>>>>>[ From mtomaz@cisco.com Fri Jan 24 16:10:48 1997 >>>>>>>>[ X-Sender: mtomaz@europe.cisco.com >>>>>>>>[ X-Mailer: Windows Eudora Pro Version 2.2 (32) >>>>>>>>[ Mime-Version: 1.0 >>>>>>>>[ Content-Type[ : [ text/plain[ ; [ charset="us-ascii"[ >>>>>>>>[ X-Priority: 1 (Highest) >>>>>>>>[ Date: Fri, 24 Jan 1997 15:09:46 +0000 >>>>>>>>[ To: Cesar Carballes >>>>>>>>[ From: Mario Tomaz >>>>>>>>[ Subject: Re: Case F34281 >>>>>>>>[ Cc: mperez@europe.cisco.com, pqueiros@europe.cisco.com, mig@convex.pt >>>>>>>>[ Content-Length: 8995 >>>>>>>>[ >>>>>>>>[ >>>>>>>>[ Cesar, >>>>>>>>[ >>>>>>>>[ The authentication process of the 765 USER seems to work properly. >>>>>>>>After >>>>>>>>[ this the 765 waits for the AS5200 to authenticate itself back to the >>>>>>>>765. We >>>>>>>>[ can't disable this last process. >>>>>>>>[ If the command "ppp pap sent-username as5200 password yyyy" is not >>>>>>>>included >>>>>>>>[ in the AS5200 configuration then the authentication process is >>>>>>>>invalid. >>>>>>>>[ Please see on my mail of 16 December the debug details. You can >>>>>>>>follow the >>>>>>>>[ authentication process. >>>>>>>>[ We have tested the same with a 765 accessing a 25xx router. The same >>>>>>happens. >>>>>>>>[ I insist that the 765 is causing this problem. There is no reason >>>>>>>>why it >>>>>>>>[ should wait for the Access server to authenticate itself back to the >>765. >>>>>>>>[ >>>>>>>>[ Miguel Teixeira of Convex has some traces captured with a Sniffer. >>>>>>>>Are you >>>>>>>>[ able to read those? Please confirm, then I will send them. >>>>>>>>[ >>>>>>>>[ This problem has been "laying arround" for quite some time now. Our >>>>>>>>customer >>>>>>>>[ has the intention of buying a lot of this access routers but we >>>>>>>>need to >>>>>>>>[ clear this situation first. >>>>>>>>[ >>>>>>>>[ What they want is the 765 to PAP authenticate itself as it >>>>>>>>accesses the >>>>>>>>[ Access Server. The authentication process should end just here. >>>>>>>>[ >>>>>>>>[ Regards, >>>>>>>>[ Mario Tomaz >>>>>>>>[ >>>>>>>>[ At 13:51 16-01-1997 +0100, you wrote: >>>>>>>>[ >Hi Mario, >>>>>>>>[ > >>>>>>>>[ >I have to apologize for the delay in answering this case, I got >>problems >>>>>>>>[ >wiht the number of critical cases I handled. Now is your turn. Sorry >>>>>>>>[ >about that. >>>>>>>>[ > >>>>>>>>[ >You may have to configure >>>>>>>>[ > >>>>>>>>[ >set ppp authentication outgoing pap >>>>>>>>[ > >>>>>>>>[ > in the 765, this should chalenge the AS5200 with the pap >>>>>>>>username and >>>>>>>>[ > password (incoming) and everything should work. >>>>>>>>[ > >>>>>>>>[ >I didn't test it in the lab because I don't have the units to do >>it, but >>>>>>>>[ >after reading the 765 command book looks to me reasoneable. >>>>>>>>[ > >>>>>>>>[ >Let me see if this fixs your problem. >>>>>>>>[ > >>>>>>>>[ >Kind Regards >>>>>>>>[ >Cesar Carballes >>>>>>>>[ > >>>>>>>>[ > >>>>>>>>[ >[ From mtomaz@cisco.com Tue Dec 24 10:40:22 1996 >>>>>>>>[ >[ X-Sender: mtomaz@europe.cisco.com >>>>>>>>[ >[ X-Mailer: Windows Eudora Pro Version 2.2 (32) >>>>>>>>[ >[ Mime-Version: 1.0 >>>>>>>>[ >[ Content-Type[ : [ text/plain[ ; [ charset="us-ascii"[ >>>>>>>>[ >[ X-Priority: 1 (Highest) >>>>>>>>[ >[ Date: Tue, 24 Dec 1996 09:34:21 +0000 >>>>>>>>[ >[ To: ccarball@cisco.com >>>>>>>>[ >[ From: Mario Tomaz >>>>>>>>[ >[ Subject: Case F34281 >>>>>>>>[ >[ Cc: pqueiros@europe.cisco.com, hcarlos@europe.cisco.com >>>>>>>>[ >[ Content-Length: 5999 >>>>>>>>[ >[ >>>>>>>>[ >[ >>>>>>>>[ >[ Cesar, >>>>>>>>[ >[ >>>>>>>>[ >[ During a visit to Telepac we did some tests and discovered that >>>>>>>>the PPP >>>>>>>>[ >[ authentication process is not working the way we expected. >>>>>>>>[ >[ A user connected to the 765 router was only able to access the >>>>>>>>AS5200 >>>>>>using >>>>>>>>[ >[ PAP authentication after the following command was issued on the >>>>>>>>AS5200: >>>>>>>>[ >[ ppp pap sent-username xxxx password yyyy >>>>>>>>[ >[ >>>>>>>>[ >[ What we realy want to achieve is the following: >>>>>>>>[ >[ A remote user (connected to a 765) dials into a AS5200. >>>>>>>>[ >[ User (PAP) authentication is done by the AS5200 (Authentication >>>>>>>>IN). >>>>>>>>[ >[ In the AS5200 the function Authentication OUT is disabled. >>>>>>>>[ >[ >>>>>>>>[ >[ During the tests we could not disable the process of PAP >>>>>>authentication OUT >>>>>>>>[ >[ on the AS5200. That is why the "ppp pap sent-username" command is >>>>>>>>needed. >>>>>>>>[ >[ The AS5200 itself expects authentication from the 765. >>>>>>>>[ >[ >>>>>>>>[ >[ Included is a document explaining the above mentioned command. >>>>>>>>[ >[ >>>>>>>>[ >[ Please let me know what to do. >>>>>>>>[ >[ >>>>>>>>[ >[ Regards, >>>>>>>>[ >[ Mario Tomaz >>>>>>>>[ >[ >>>>>>>>[ >[ > PPP Authentication Changes >>>>>>>>[ >[ > >>>>>>>>[ >[ >Several requests have come in for modifications to the PPP >>>>>>Authentication >>>>>>>>[ >[ >feature. At the same time, a fundamental security hole >>>>>>>>(remote PAP >>>>>>gives >>>>>>>>[ >[ >away the router's hostname and matching password) was identified. >>>>>>>>Here >>>>>>>>[ >[ >are the changes made. Note that three DDTS were opened >>>>>>>>(CSCdi49278, >>>>>>>>[ >[ >CSCdi54088 and CSCdi44884). These changes were integrated into >>>>>>11.0(8.1), >>>>>>>>[ >[ >11.1(3.0.2) and 11.2(0.7). >>>>>>>>[ >[ > >>>>>>>>[ >[ > For the purposes of this document, 'remote authentication' >>>>>>>>will mean >>>>>>>>[ >[ > authentication BY the remote PPP unit of the local router. >>>>>>Similarly, >>>>>>>>[ >[ > 'local authentication' is the authentication OF the remote PPP >>>>>>unit by >>>>>>>>[ >[ > the local router. The unit doing the authentication (the >>>>>>authenticator) >>>>>>>>[ >[ > is the unit checking the other ends password. Another way of >>>>>>looking >>>>>>>>[ >[ > at it is that the terms, 'local' and 'remote', refer to the >>>>>>location of >>>>>>>>[ >[ > the applicable 'ppp authentication {chap|pap}' configuration >>>>>>command. >>>>>>>>[ >[ > The terms 'local authentication' and 'remote >>>>>>>>authentication' are >>>>>>>>[ >[ > confusing but slightly better than 'inbound >>>>>>>>authentication' and >>>>>>>>[ >[ > 'outbound authentication'. >>>>>>>>[ >[ > >>>>>>>>[ >[ > >>>>>>>>[ >[ >Goals: >>>>>>>>[ >[ > -disable remote PAP authentication unless explicitly >>>>>>>>configured >>>>>>>>[ >[ > -allow multiple servers to appear as a single server >>>>>>>>to ease >>>>>>configs >>>>>>>>[ >[ > -allow remote peer to authenticate to multiple unknown >>>>>>>>servers >>>>>>>>[ >[ > >>>>>>>>[ >[ >New PPP Authentication Commands >>>>>>>>[ >[ > >>>>>>>>[ >[ > ppp pap sent-username xxxx password yyyy >>>>>>>>[ >[ > ppp chap hostname xxxx >>>>>>>>[ >[ > ppp chap password [n] zzzz >>>>>>>>[ >[ > >>>>>>>>[ >[ > All commands are interface configuration commands. Since >>>>>>>>they are >>>>>>>>[ >[ > PPP commands they are entered in the dialer group or async >>>>>>>>group or >>>>>>>>[ >[ > BRI/PRI interface as applicable. >>>>>>>>[ >[ > >>>>>>>>[ >[ > ppp pap sent-username xxxx password yyyy >>>>>>>>[ >[ > >>>>>>>>[ >[ > Remote PAP has been disabled by default. This command >>>>>>>>will re- >>>>>>>>[ >[ > enable remote PAP support for the specific interface and >>>>>>>>use the >>>>>>>>[ >[ > 'sent-username' and 'password' in the PAP Authentication >>>>>>>>Request >>>>>>>>[ >[ > packet to the peer. Remote PAP is when the peer requests >>>>>>that you >>>>>>>>[ >[ > authenticate or prove yourself to him. This change >>>>>>>>was done >>>>>>because >>>>>>>>[ >[ > a security hole exists in the present code. Prior to this >>>>>>change, >>>>>>>>[ >[ > we would send out our hostname and password in the PAP >>>>>>>>[ Authentication >>>>>>>>[ >[ > Request packet. The same password that the peer is >>>>>>>>supposed to >>>>>>>>[ >[ > know in order to do local CHAP authentication. >>>>>>>>[ >[ > >>>>>>>>[ >[ > ppp chap hostname xxxx >>>>>>>>[ >[ > >>>>>>>>[ >[ > This command is added to allow ISPs to create a pool of >>>>>>>>dial-up >>>>>>>>[ >[ > routers all appearing to be the same host when >>authenticating >>>>>>>>[ >[ > with CHAP. Currently, the ISP's customers need to have >>>>>>>>username >>>>>>>>[ >[ > entries for any possible router they might attach to. >>>>>>>>This will >>>>>>>>[ >[ > allow them to have a single entry as all ISP routers will >>>>>>challenge >>>>>>>>[ >[ > with a common hostname. This command is normally used >>>>>>>>with >>>>>>local >>>>>>>>[ >[ > CHAP authentication (when we are authenticating the peer) >>>>>>>>but it >>>>>>>>[ >[ > can also be used for remote authentication. >>>>>>>>[ >[ > >>>>>>>>[ >[ > ppp chap password [n] zzzz >>>>>>>>[ >[ > >>>>>>>>[ >[ > This command is added to allow a router dialing to a >>>>>>collection of >>>>>>>>[ >[ > routers not supporting the 'ppp chap hostname xxxx' >>>>>>>>command >>>>>>(such >>>>>>>>[ >[ > as units running older IOS images) to configure a common >>>>>>password >>>>>>>>[ >[ > (ie CHAP secret) to use in responding to challenges >>>>>>>>from an >>>>>>unknown >>>>>>>>[ >[ > peer. Thus a customer can replace several >>>>>>>>username/password >>>>>>config >>>>>>>>[ >[ > commands with a single copy of this command (per >>interface or >>>>>>>>[ >[ > dialer/async group interface). Note that this command is >>>>>>only used >>>>>>>>[ >[ > for remote CHAP authentication, ie. when we are >>>>>>authenticating for >>>>>>>>[ >[ > the peer. It does not affect local CHAP authentication. >>>>>>>>[ >[ > >>>>>>>>[ >[ > >>>>>>>>[ >[ >Example configurations (most non-authentication details left out) >>>>>>>>[ >[ > >>>>>>>>[ >[ > Remote router dialing multiple servers in a single rotary >>>>>>>>(w/out >>>>>>dialin) >>>>>>>>[ >[ > >>>>>>>>[ >[ > hostname customer451 >>>>>>>>[ >[ > ! >>>>>>>>[ >[ > interface bri0 >>>>>>>>[ >[ > encap ppp >>>>>>>>[ >[ > ppp chap password 7 jfdjla >>>>>>>>[ >[ > >>>>>>>>[ >[ > Central site router (one of many in a single rotary) >>>>>>>>[ >[ > >>>>>>>>[ >[ > hostname 3rdfromtop >>>>>>>>[ >[ > ! >>>>>>>>[ >[ > username customer451 password 7 jfdjla (probably uses >>>>>>>>TACACS+ >>>>>>>>[ >[ instead) >>>>>>>>[ >[ > ! >>>>>>>>[ >[ > interface dialer0 >>>>>>>>[ >[ > encap ppp >>>>>>>>[ >[ > ppp authentication chap callin >>>>>>>>[ >[ > ppp chap hostname ISPCorp >>>>>>>>[ >[ > >>>>>>>>[ >[ > Central site router (as above but requiring support for >>older PAP >>>>>>>>[ clients) >>>>>>>>[ >[ > >>>>>>>>[ >[ > hostname 3rdfromtop >>>>>>>>[ >[ > ! >>>>>>>>[ >[ > username customer451 password 7 jfdjla (probably uses >>>>>>>>TACACS+ >>>>>>>>[ >[ instead) >>>>>>>>[ >[ > ! >>>>>>>>[ >[ > interface dialer0 >>>>>>>>[ >[ > encap ppp >>>>>>>>[ >[ > ppp authentication chap pap callin >>>>>>>>[ >[ > ppp chap hostname ISPCorp >>>>>>>>[ >[ > ppp pap sent-username ISPCorp password 7 fjhfeu >>>>>>>>[ >[ >>>>>>__________________________________________________________________________ >>>>>>>>[ >[ >>>>>>>>[ >[ Mario Tomaz, Systems Engineer >>>>>>>>[ >[ Cisco Systems Phone: +351 1 3404531/2 >>>>>>>>[ >[ Av.da Liberdade,114/134 Fax: +351 1 3404569/75 >>>>>>>>[ >[ 1250 Lisboa Mobile: +351 931 356824 >>>>>>>>[ >[ PORTUGAL E-mail: mtomaz@europe.cisco.com >>>>>>>>[ >[ >>>>>>__________________________________________________________________________ >>>>>>>>[ >[ >>>>>>>>[ > >>>>>>>>[ >>>>>>>>_______________________________________________________________________ >>>>>>>>___ >>>>>>>>[ >>>>>>>>[ Mario Tomaz, Systems Engineer >>>>>>>>[ Cisco Systems Phone: +351 1 3404531/2 >>>>>>>>[ Av.da Liberdade,114/134 Fax: +351 1 3404569/75 >>>>>>>>[ 1250 Lisboa Mobile: +351 931 356824 >>>>>>>>[ PORTUGAL E-mail: mtomaz@europe.cisco.com >>>>>>>>[ >>>>>>>>_______________________________________________________________________ >>>>>>>>___ >>>>>>>>[ >>>>>>>> >>>>>>> >>>>>>__________________________________________________________________________ >>>>>> >>>>>> Mario Tomaz, Systems Engineer >>>>>>Cisco Systems Phone: +351 1 3404531/2 >>>>>>Av.da Liberdade,114/134 Fax: +351 1 3404569/75 >>>>>>1250 Lisboa Mobile: +351 931 356824 >>>>>>PORTUGAL E-mail: mtomaz@europe.cisco.com >>>>>>__________________________________________________________________________ >>>>> >>>>> >>>>> _______________________________________________________ >>>>>* * >>>>>* Bruce Laird * >>>>>* Marketing Director, Access Business Unit * >>>>>* * >>>>>* Phone: 408-526-4876 | | * >>>>>* Fax: 408-527-3778 ||| ||| * >>>>>* Email: laird@cisco.com ||||| ||||| * >>>>>* Snail: 170 W. Tasman Drive ..:|||||||:..:|||||||:.. * >>>>>* San Jose, CA 95134 Cisco Systems, Inc. * >>>>>*_______________________________________________________* >>>>> >>>> >>>> >>>> >>>> >>>> __\/__ >>>> . / ^ ^ \ . >>>> |\| (o)(o) |/| >>>>#-.OOOo----oo----oOOO.-----------------------------------------------------# >>>># Jean J. Zuo | | # >>>># PME - ABU Marketing ||| ||| # >>>># Phone: (408) 526-4424 .:|||:. .:|||:. # >>>># Pager: (408) 815-4089 Cisco Systems Inc. # >>>>#____________Oooo._________________________________________________________# >>>> .oooO ( ) >>>> ( ) ) / >>>> \ ( (_/ >>>> \_) >>>> >>> >>> >>> >>> >>> __\/__ >>> . / ^ ^ \ . >>> |\| (o)(o) |/| >>>#-.OOOo----oo----oOOO.-----------------------------------------------------# >>># Jean J. Zuo | | # >>># PME - ABU Marketing ||| ||| # >>># Phone: (408) 526-4424 .:|||:. .:|||:. # >>># Pager: (408) 815-4089 Cisco Systems Inc. # >>>#____________Oooo._________________________________________________________# >>> .oooO ( ) >>> ( ) ) / >>> \ ( (_/ >>> \_) >>> >>> >>__________________________________________________________________________ >> >> Mario Tomaz, Systems Engineer >>Cisco Systems Phone: +351 1 3404531/2 >>Av.da Liberdade,114/134 Fax: +351 1 3404569/75 >>1250 Lisboa Mobile: +351 931 356824 >>PORTUGAL E-mail: mtomaz@europe.cisco.com >>__________________________________________________________________________ > > > _______________________________________________________ >* * >* Bruce Laird * >* Marketing Director, Access Business Unit * >* * >* Phone: 408-526-4876 | | * >* Fax: 408-527-3778 ||| ||| * >* Email: laird@cisco.com ||||| ||||| * >* Snail: 170 W. Tasman Drive ..:|||||||:..:|||||||:.. * >* San Jose, CA 95134 Cisco Systems, Inc. * >*_______________________________________________________* > > Lisbon Office Pedro Amorim Queiros Phone - 351 1 3404531 Fax - 351 1 3404575 Mobile - 351 931 310089